Skip to main content
TrustRadius
Liquibase

Liquibase

Starting at $5,000 per year
View Pricing

Overview

What is Liquibase?

Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more…

Read more
Recent Reviews
Read all reviews

Awards

Products that are considered exceptional by their customers based on a variety of criteria win TrustRadius awards. Learn more about the types of TrustRadius awards to make the best purchase decision. More about TrustRadius Awards

Reviewer Pros & Cons

View all pros & cons
Return to navigation

Pricing

View all pricing

Entry-level set up fee?

  • No setup fee
For the latest information on pricing, visithttps://www.liquibase.com/pricing

Offerings

  • Free Trial
  • Free/Freemium Version
  • Premium Consulting/Integration Services

Starting price (does not include set up fee)

  • $5,000 per year
Return to navigation

Product Details

What is Liquibase?

Liquibase is a database change management tool that helps teams release software faster and safer by bringing the database change process into existing CI/CD automation. According to the 2021 Accelerate State of DevOps Report, elite performers are 3.4 times more likely to incorporate database change management into their process than low performers. Liquibase delivers DevOps for the database.

Liquibase value proposition:

  • Liquibase speeds up the development process. The vendor states that teams that use Liquibase deploy 233% more often. Liquibase helps teams break through the database bottleneck of manual reviews to get features to customers faster.

  • Liquibase aims to eliminate database code errors, boasting a 94% reduction in errors. Liquibase allows teams to fully test and roll back database changes before they get to production.

  • Liquibase empowers teams to collaborate. By treating database code like application code, Liquibase is designed to make it easier for app developers to work with the database team leveraging the same tools that they’re already comfortable with.

  • No one enjoys missing date night or a dance recital because the database deployment failed. Many teams rely on DBAs and database developers to fix issues and manually review code 24/7. Liquibase helps automate tedious manual, error-prone processes so that the database team can focus on more important tasks.

Liquibase Editions

Liquibase offers several editions to meet the needs of developers, software teams, and organizations of all shapes and sizes.

Solutions Ideal for Cloud Native and Hybrid Data Applications

Liquibase Open Source

The Liquibase Open Source project started in 2006. Downloaded over 100M times, it continues to be the most powerful and most widely used open source database version control software for developers on the planet. Liquibase Open Source provides developers the ability to treat database changes as code so that they can version and deploy them along with application code.

Liquibase Pro

Liquibase Pro is presented as ideal for agile, iterative development in cloud-native, microservices, and hybrid data environments. Liquibase Pro brings database and security teams into your DevOps process - promoting database standardization, quality, and compliance within CI/CD automation across more than 50 database platforms. Built on the foundation of Liquibase Open Source, Liquibase Pro provides additional capabilities and services including:

  • Pre- and post-deployment validation to enable continuous compliance, governance, and security - bringing the database and security teams into the DevOps process

  • Workflow modularity and portability to abstract and standardize practices across projects, teams, and toolchains

  • Native Amazon S3 integration to support secure and governed centralization of Liquibase artifacts to support all projects.

  • Support for native database executors, such SQL*Plus, sqlcmd, and psql

  • Advanced versioning and rollback capabilities

  • Centralized auditing, visibility, and metrics through Liquibase Hub

  • Expert support and guidance from the creators of Liquibase.

A Solution for Mission-Critical Transactional Applications

Liquibase Enterprise

Liquibase Enterprise is built to provide enterprise reliability and security for mission-critical, relational databases typical in high transaction environments. Presented as ideal for businesses in highly regulated industries, Liquibase Enterprise offers advanced rules and deployment checks for automated speed, safety, and compliance. Organizations that require database reliability can use Liquibase Enterprise to forecast the impact of changes on a target database before any change is made.

Liquibase Enterprise supports enterprise database platforms: Oracle, SQLServer, IBM DB2, EnterpriseDB, PostgreSQL.

Liquibase Integrations

Liquibase Competitors

Liquibase Technical Details

Deployment TypesOn-premise
Operating SystemsWindows, Linux, Mac
Mobile ApplicationNo

Liquibase Downloadables

Frequently Asked Questions

Liquibase starts at $5000.

Redgate Flyway, DBmaestro Database DevOps Platform, and Redgate SQL Provision are common alternatives for Liquibase.

Reviewers rate Support Rating highest, with a score of 8.

The most common users of Liquibase are from Enterprises (1,001+ employees).

Liquibase Customer Size Distribution

Consumers0%
Small Businesses (1-50 employees)10%
Mid-Size Companies (51-500 employees)40%
Enterprises (more than 500 employees)50%
Return to navigation

Comparisons

View all alternatives
Return to navigation

Reviews and Ratings

(94)

Attribute Ratings

Reviews

(1-25 of 30)
Companies can't remove reviews or game the system. Here's why
August 21, 2023

Liquibase is an open-source database migration tool that helps developers manage and version their database schema change

PL
Peter Lu
Senior Backend Engineer
Skiff (Computer Software, 201-500 employees)
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
Change log management organize and database changes in a systematic manner. Changes are organized into a series of change sets, each representing a specific change or a set of related changes.
Pros and Cons
  • Each change log file contains one or more change sets.
  • A change set represents a specific database modification ( like adding a table, altering a column).
  • Liquibase seamlessly integrates with continuous integration and continuous deployment (CI/CD) pipelines.
  • It enables fully automated and consistent deployments by automatically applying the necessary database changes along with code changes, minimizing deployment-related errors.
  • For large databases with extensive change logs, applying changes can sometimes lead to performance issues
  • Enhancements in performance optimization could help reduce execution times, especially for deployments involving significant schema modifications.
Likelihood to Recommend
In microservices architectures, each service may have its own database schema. Liquibase excels in managing schema changes for individual services, allowing for independent updates while keeping overall consistency.
July 12, 2023

Liquibase Fixes A Problem Everyone Has But Doesn't Know There's An Answer For

JA
Joe Albano
Senior Configuration Management Advisor
General Dynamics Information Technology (Information Technology & Services, 10,001+ employees)
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
Liquibase brought our database changes and data correction processes up to speed with our code deploys which were already automated. It allows us to rely on automated validation as well as fit into our current software development lifecycle processes and CM software using a central versioned artifact capable of being deployed through our current CD pipeline.
Pros and Cons
  • Rule checking and validation of SQL
  • Forecasting of changes to databases
  • Report generation and console dashboard oversight of DB changes
  • Agnostic to git repo choices (for the most part)
  • Upgrade/install process is very manual unless you take the time to script it
  • Rule changes are done through commits to repo
  • Setting up pipelines is a bit cumbersome
Likelihood to Recommend
Liquibase is great for automating a variety of database changes and updates while constraining users through a validation build process. While setup of the product can be a bit tedious or cumbersome, once in place, it produces fantastic returns for developers, DBAs, and CM personnel as each part of the process becomes aligned with a typical CI/CD for code deploys.
July 10, 2023

Liquibase is a decent DB release management tool with good capabilities.

Verified User
Engineer in Engineering
Hospital & Health Care Company, 1001-5000 employees
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
Liquibase is used as a Database Release Management Tool. We have a multi-tenant solution where different customers have different RDBMS systems but the same DB structure. Liquibase is used to have a single repo with multiple types of targets.
Pros and Cons
  • Support Multi-type Target DBs.
  • Works well for Tables but not much for Functions, Stored Procedures, etc.
  • DMLs are not supported in JSON format to be a single source.
Likelihood to Recommend
Liquibase is used as a Database Release Management Tool. We have a multi-tenant solution where different customers have different RDBMS systems but the same DB structure. Liquibase is used to have a single repo with multiple types of targets. It is great for DDL, esp. Tables. But it lacks JSON files like single repo code/source support with DMLs and other DB objects.
July 10, 2023

Liquibase Pro Trial for Squad

Verified User
Employee in Engineering
Financial Services Company, 51-200 employees
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We needed a method for version control across development environments. Liquibase helped solve this issue and made creating new database instances on local machines extremely easy using docker. Liquibase also gave an easy method to destroy and rebuild development environments such as QA and DEV to match what we use in production.
Pros and Cons
  • Giving Version Control
  • Creating New Instances of Database Environments
  • Rollback Changes
  • Checking for Common SQL Errors
  • Pro Sales Team didn't seem to interested in selling the pro service to us.
  • The subscription license for Pro seemed extremely short for the time to see features in action.
  • Liquibase is great at setting up new environments, but you pay for each database for each environment. In the case of trying to use Liquibase locally as a team, you would have to pay for each dev machine. Needs a better pricing model that plays into using Liquibase at its fullest potential without getting penalized.
  • Needs price breaks after so many instances. 1-10 cost, 10-50 cost, 50-200 cost, ect.
Likelihood to Recommend
Liquibase works well for smaller size companies currently with fewer development environments. Since you have to pay per database on each environment and there are no breaks in the cost as the databases increase. The product works great for version control, rollbacks, error checking, and recreating instances of environments. Liquibase was easy to learn, and they had a lot of documentation explaining how to use their product.
July 09, 2023

Onestop solution for Database Deployments…!!!

Verified User
Professional in Information Technology
Banking Company, 10,001+ employees
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We are using Liquibase to manage our database deployment, which helps us to achieve proper tracking of deployments and enable better troubleshooting/rollback strategy. Most of the application teams are interested in adopting it based on internal assessment, which helps us to enable devops culture in our organization. This tool is definitely a game changer and has less involvement from the DBA end once configured kind of one-time setup, and app teams can take care of the rest of the things.
Pros and Cons
  • Less Complex Configuration.
  • Easily to Integrate.
  • Multiple DB Platforms.
  • DB Monitoring along with Deployment.
  • PAM Tool integration.
  • CI/CD
Likelihood to Recommend
Every week we receive 10-15 manual database and complex database deployment requests, which are quite difficult for DBA to support apart from other routine administration tasks. This problem we managed to solve with the help of Liquibase integration. This single tool is cable to take database deployments on SQL and NO-SQL databases which is a great advantage for any Organisation.
July 09, 2023

Liquibase, a full DevOps database deployment tool.

Verified User
Team Lead in Engineering
Financial Services Company, 10,001+ employees
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
During our DevOps implementation challenge for the database, we evaluated different tools, and Liquibase allowed us to have the highest number of compatible database engines. Today, we have applications that perform up to 4 automated, decentralized, and traceable deployments daily. Throughout this process, we received perfect continuous support from the Liquibase team.
Pros and Cons
  • DDL, DML deployments.
  • Forecast changesets between environments.
  • GIT compatible.
  • Compatibility with ORACLE, DB2, MSSQL, MySQL, PostgreSQL.
  • License compatibility between Enterprise and PRO (MySQL Support).
Likelihood to Recommend
Until now, Liquibase has had good support for structured database types, and they are currently working on features for non-SQL databases.
July 09, 2023

Our experience implementing and using Liquibase Pro.

Verified User
Team Lead in Information Technology
Utilities Company, 1001-5000 employees
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We using Liquibase to promote changes in DB's from Development landscape to others, including Production Systems. Liquibase is orchestrated in a Ci/Cd pipeline in a DevSecOps scenario. When the lifecycle of a product/application includes code and DB changes, Liquibase is perfect for managing it. We are using it, too, to manage versions in DB changes.
Pros and Cons
  • Version Management en DB changes.
  • Move DB changes to other changes, including rollbacks.
  • Improve good practices in our development teams.
  • Ability to move DB changes to several landscapes consistently.
  • Manage DB change versions using GIT repositories.
  • Join DB Changes and Code in the same Ci/Cd pipeline.
Likelihood to Recommend
We need to change "the culture" and management of change in our Teams to apply the best practices embedded in Liquibase. After this change process, the benefits appear. In many cases, we evaluate the pros/cons of using Liquibase in applications, considering complexity and change rates. Finally, applying ROI before implementation is useful to us.
July 01, 2023

Liquibase maximizes development team with faster deployment

BM
BISWA MAHAPATRA
Lead DBA
Costar Group (Real Estate, 1001-5000 employees)
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
An ease of error-prone and quick database deployments both on-prem and on cloud integrated with CI/CD DevOps Automation.
Pros and Cons
  • Difference of Schemas between two databases
  • Baseline on a newer target deployment
  • Well fit in with dockers and Azure Devops for CI/CD Automation Deployment
  • Snapshots being a great feature on offline diff but need to come up with strong reliability outcome
  • Sequences And Unique Constraints outcome from diff changelog is redundant
Likelihood to Recommend
Our POC based on other competing tools definitely Liquibase gets a mileage and it's helping our development team for quick and error-free schema deployment on Cloud/Hybrid database targets.
June 30, 2023

Liquibase - Simplifying DB change management

Verified User
Team Lead in Engineering
Hospital & Health Care Company, 10,001+ employees
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We are using Liquibase for maintaining our mysql database changes. Liquibase has made our db deployments quite simple and maintainable. Using changelogs it makes it very easy to be used by multiple developers at same time, without stepping over each other. It provide a rollback mechanism to undo any unwanted changes. It can be easily integrated with spring boot application.
Pros and Cons
  • Supports multiple databases.
  • Supports multiple file formats like json, xml, yaml and sql
  • Integration with various frameworks like Spring boot, maven etc
  • We couldn't find a way to configure liquibase pro key in a spring boot project
Likelihood to Recommend
Earlier we were using manual db deployments which were very time consuming. With Liquibase it made the CI-CD pipelines quite simple. Deployments which earlier used to take around and hour are now completed within couple of minutes.
December 22, 2022

Excellent & Powerful Tool

Verified User
Team Lead in Information Technology
Information Technology & Services Company, 1001-5000 employees
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We use Liquibase to control the version of SQL scripts, source code, deployment, and (if required) rollback of database changes. We were able to go from manually tracking arbitrary SQL changes to having a reliable, repeatable, and precise representation of the contents of our database structure thanks to its help. It lessens the manual work and helps us update clients via the Jenkins pipeline.
Pros and Cons
  • It's a useful tool for managing database versions and aiding in the development of database CI/CD pipelines.
  • The deployment and management of database updates are simple.
  • It provides quality checks to spot problems in DB scripts and DB pipeline views to track changes made to DB.
  • The community version has very few features enabled.
  • Using a time-series of logs chart, you can figure out how often changes happen and how much risk there is.
  • Further develop documentation and use case models
Likelihood to Recommend
One of the features that I think is useful is the support for various rollback scenarios and multi-DB support. They also pay attention to their clients, and I believe that the quality metrics feature enables us to apply rules and coding standards specific to our organization. It provides DB pipeline views for changes deployed to DB and quality checks for DB scripts, both of which aid in error detection.
December 15, 2022

Liquibase Review

Verified User
Engineer in Information Technology
Information Technology & Services Company, 1001-5000 employees
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We used Liquibase in CI/CD for DB update and modification. We have implemented Liquibase with Oracle as the database, Jenkins for CI/CD and Github to ensure the modification of database changes faster and safer on all environments. With help of Liquibase its very convenient to update and modify DB on the go.
Pros and Cons
  • Easy to implemnent
  • Work with different DBs.
  • DB Versioning
  • Supports of NoSQL DBs as well.
  • Rollbacks
  • Supports SQL, YAML, XML and JSON
  • missing detail loging
  • PLSql not supported
Likelihood to Recommend
Automating DB deployment. Supports multiple DBs like Oracle, SQL Server etc. Specially if you have different sets of Databases for your environments like Dev, QA, UAT or Prod, in this case Liquibase help greatly with changing and modification of database.
December 15, 2022

Centralize database changes with Liquibase

Verified User
Advisor in Information Technology
Government Administration Company, 201-500 employees
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
Our database admins lacked some central controls to manage different type of databases like Oracle, Microsoft SQL and MySQL
We were searching for tools and found Liquibase. As Liquibase has an open source offering it looked like the right tool to explore our exact needs.

While we grew into the tool, the forums and the documentation we grew attached to Liquibase and decided to stay with the product for managing our change control on the different database types and go for the Pro offering to get standard support and some additional security automation.
Pros and Cons
  • One console to manage different types of database platforms
  • simplicity
  • Offers extensive knowledge sharing
  • They could expand the product features a bit more
  • Attract more partners
Likelihood to Recommend
Liquibase is best suited if you have a diverse database ecosystem of your own where you are in charge of all the development changes and testing. If you only maintain databases from suppliers this tool is probably not for you.
December 09, 2022

Using Liquibase docker image for database schema migration

Verified User
Consultant in Information Technology
Information Technology & Services Company, 1001-5000 employees
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
Liquibase enables database schemas migration and rollbacks, it is used with other products (GCP SQL & SQL Auth Proxy) in a Kubernetes environment
Pros and Cons
  • Schema migration
  • Schema rollback
  • Error logging
  • Changing already played scripts
Likelihood to Recommend
Liquibase is well suited for migrating and rollbacking database schemas.
It is XML based which makes it easy to read and mantain.
It also gives a great view of the database schema at a given point.
Issues related to this service are mainly due to the time it takes to update schema and error logging which is not always great.
December 09, 2022

Liquibase the foundation of devops

Verified User
Engineer in Manufacturing
Automotive Company, 5001-10,000 employees
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Pros and Cons
  • Ease of Use
  • Cost effective
  • Quality of support
  • Server costs and expenses
  • Improvement in GUI
  • Backup
Likelihood to Recommend
Liquibase delivers database devops by bringing database change into existing CI/CD pipelines. Liquibase Liquibase speeds up the development process and that is the most appalling feature of it. It helps our development team to break through the database bottleneck of manual reviews easily to get features to customers faster which ensures quality delivery of services at the right time and right price.
December 08, 2022

LIquibase DevOps database: Control your project from Planning to Deliver with continous improvement and RISK free

Fernando Roque | TrustRadius Reviewer
Fernando Roque
Statistical Analyst
Amplitude & Statistics (Information Technology & Services, 1-10 employees)
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
DevOps is the acronym for Developer and Operations, a concept that integrates the IT department with other engineering areas like logistics, marketing, and sales. DevOps software writing and delivery phases are Planning, Developing, Delivering, and Operating. Each step requires tracking every change done to the IT systems. This change log requirement involves the use of a database tracking the table modifications. Liquibase can work with the major database of the market like Oracle, SQL Server, and Mysql to maintain a change log.
Pros and Cons
  • Alter database tables logs.
  • Connection to major database with JDBC (ex. MySql, SQL Server, Oracle)
  • Text Description of the change with user and ID information.
  • Work with SAP Hana database.
  • Gropuing chart of change logs to identify users and description with more changes.
  • Time-Series of logs chart to identify the frequency of the changes and measure the RISK.
Likelihood to Recommend
The Liquibase application is helpful in keeping the Developer's Operation (DevOps) steps change logs and checking if the software development is following the guidelines defined during the Planning step. Liquibase keeps track of every table alteration during the Develop, Deliver, and Operate activities of the software writing and delivering. The change logs help to do a continuous delivery and also to research Security and Compliance. It would be helpful the integration with SAP Hana because it works with online transactions and business intelligence at the same time. It is necessary to keep track of the reports from the ERP and the Data Warehousing.
December 08, 2022

Must have tool for DevOps

ML
Ming Li
CEO (Chief Executive Officer)
Ming Microsystems (Computer Software, 1-10 employees)
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We use liquibase to help manage database versioning associated with application versioning. When we update our software application, sometimes, there are associated database changes that need to be applied. One key requirement in our business is that we need to be very agile to meet the rapid needs of our end users. Having liquibase allows us to be agile and deliver high quality app. Liquibase also ensures the integrity of database with respect to application. When we deploy a new application, we bake liquibase into our CI/CD so that any database changes are applied together with application deployment.
Pros and Cons
  • easy to use
  • easy to onboard new developers
  • works as intended
  • easy to manage
  • works well with CI/CD tools
  • too much initial configuration in some places
  • documentation lacking on some aspects
  • limited support
Likelihood to Recommend
Liquibase is suited if you have a database and the application you write is highly dependent on that database. If your application doesn't require a database, then you don't need liquibase. You should only use liquibase to apply database changes that are associate with any application change. If you want to apply a change to database to resolve a production incident without changing the application, then you should not be using liquibase.
December 08, 2022

Liquibase Helps Us Ensure Trust, Confidence, and Accuracy in Our Database Deployments

David Williams | TrustRadius Reviewer
David Williams
Head of Engineering
Damstra Technology (Information Technology & Services, 51-200 employees)
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We use Liquibase to handle version control and source code control of SQL scripts and database changes and for the deployment and (if needed) rollback of the same. It's helped us go from arbitrary SQL changes that we tried to manually track, to having a reliable, repeatable, accurate account of what's in our database structure.
Pros and Cons
  • database as code
  • version control
  • deployment
  • rollback
  • Sometimes the syntax is a little fiddly
  • Sometimes it is not clear the best way to modify a previous script; i.e. adjust it or make a new one to correct the issue
Likelihood to Recommend
It's a great tool to use when you have scriptable changes that you know really must be under source code control but often aren't. It's also excellent to use for a team so everybody has a repeatable and accurate source of truth, but it definitely should be used by lone developers too. Everyone should be using version control for their infrastructure and database changes and Liquibase makes it easy to do this.
November 23, 2022

Liquibase made more than I thought

Gabriel Marañon Rodriguez | TrustRadius Reviewer
Gabriel Marañon Rodriguez
DevOps Engineer
Banco Ganadero (Banking, 1001-5000 employees)
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
No database scripts versioning procedures. With liquidbase we implement a procedure for database script actualization.
Pros and Cons
  • Keep track of changes
  • Rollbacks
  • Documentation
  • Using with existing database
  • Generating changesets for special objects
Likelihood to Recommend
Organized databases with few schemas or instances.
September 14, 2022

Liquibase? More like Liquib-ACED!

Mitchell Cooper | TrustRadius Reviewer
Mitchell Cooper
Data Engineer
PayIt (Financial Services, 51-200 employees)
Score 10 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
Liquibase has helped us with implementing reliable version control and a CI/CD pipeline for our data warehousing needs. The space for database version control leaves a lot to be desired, but thankfully Liquibase has that covered! We have paired Liquibase with GitHub and GitHub actions to reliably ensure all of our environments are in sync and easily track our deployments.
Pros and Cons
  • Version Control.
  • Deployments
  • Ease of Use.
  • It would be nice to have more control over repo/changelog structure configuration and changelog deployment order.
  • Documentation around the .sql file changelogs leaves some to be desired - there is some nuance that is not explained adequately in the documentation.
Likelihood to Recommend
Liquibase works really well for CI/CD and version control if configured properly. It did take a lot of tweaking and reworking some items to really understand a lot of how the pieces fit together. I wouldn't recommend using it without pairing it with GitHub or other source control repo applications though. It feels like it really shines when working in tandem.
August 09, 2022

A tool worth trying - To improve your CD

Verified User
Team Lead in Information Technology
Information Technology & Services Company, 10,001+ employees
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
Liquibase is used by our client (in the financial domain) as part of their technology refreshment to minimize the manual effort of deploying database changes. We have integrated Liquibase with our current deployment tool uDeploy to create a continuous delivery model for deploying database changes till Production. With Liquibase in place, a couple of benefits that we have seen: To be in CD delivery, app teams are now maintaining the DB changes in version control. Make sure that came changesets are being deployed & tested across all environments till Prod. It has reduced the manual DBA effort & risk of fat-finger errors as being part of the automation of changesets deploy. Easier to adopt across all teams using different DB tools (SQL, Oracle, etc) DB changesets are now part of the quality process (running different scans as part of CI) Easier to push any changes to the Database. It is easier to roll back ANY changes (though the team needs to have rollback scripts in place with each changeset that they are deploying to achieve it). The only thing that we have observed is a compatibility issue, where we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9. It's a good tool to start implementing & tracking your database changes through Liquibase and teams should explore it from their end to ensure it fits all their requirements.
Pros and Cons
  • Tracking changes through DATABASECHANGELOG table
  • Works with different DB tools (Oracle, SQL etc.)
  • Rollbacks are easier with tag if you have rollback scripts in place.
  • Comparing databases (in different environments) or their states or even creating a new data base with existing changesets.
  • Reducing Compatibility issues, when we upgraded Liquibase from 4.2 to 4.9. The same changeset which we were able to run on successfully using 4.2, part of it was now failing when tried to deploy using 4.9
  • We are not able to see detailed logs (for different changes) in uDeploy when deploying changes through Liquibase
  • Liquibase should rollback the if any one of the changes fails.
Likelihood to Recommend
It is easier to roll back ANY changes (though the team needs to have rollback scripts in place with each changeset that they are deploying to achieve it). Tracking changes in DB itself for each schema. It helped us to reduce the manual effort for deploying changes Making sure that the same changesets are being deployed & tested across all environments till Prod
August 09, 2022

Liquibase - Why it worked for my Team

PL
Pratik Lamsal
DevOps Engineer
Moffitt Cancer Center (Health, Wellness and Fitness, 5001-10,000 employees)
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We use Liquibase to maintain our changelogs while transforming our data in snowflake and deploying it to test and prod. Liquibase changelogs help us keep up to date with our changes and do the rollback in case of any error. Liquibase also provides many validation features that will come in handy if you want to establish checks during your code deployment. It's a great product with excellent customer service.
Pros and Cons
  • Maintain chagelogs
  • Validation checks
  • Rollback changes
  • Keeps track of changes in Changelog file
  • Maybe add some features that would give customers little freedom to change a few things in case of some checksum errors.
Likelihood to Recommend
It works great for the mid-sized team, while you should plan a little better while maintaining your changes for the large group because the order does matter in liquibase deployment, so you want to be very consistent while deploying your changes. Otherwise, you will get a checksum error, which can cause you some delay in fixing that. Plus, your team should be fond of the database migration process, not the state change migration. So in the latter case, the runonchange parameter will work great for you.
August 08, 2022

Liquibase you must use it.

Verified User
Administrator in Information Technology
Computer Software Company, 1001-5000 employees
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
The most important thing is zero downtime of DB upgrades with tags. It allows us to tag, which saves huge time for taking DB backups and also Deployment downtime. Yes, it is very, very easy. Trust me; we enjoy it a lot. Also, there are rollback options, too we are so happy to use Liquibase.
Pros and Cons
  • Db tags.
  • Rollback
  • Zero downtime.
  • Supported all DB.
  • May be less code.
  • Auto rollback.
  • Less developer work.
  • Platform as a service.
Likelihood to Recommend
Zero downtime is achieved with the help of Liquibase. Also, we used to tag the current state of DB. Moreover, we are using it mainly for rolling back if anything goes wrong during Deployment, and yes, I got certified too. We love using it, and still, we are recommending it to all my team.
July 27, 2022

Need a full control on your databases? - Use Liquibase.

MM
MANAS MONDAL
Lead Solution Architect
Unisys (Information Technology & Services, 10,001+ employees)
Score 9 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
Unisys is planning to use Liquibase for managing revisions of database schema scripts for their existing/ upcoming clients.
Pros and Cons
  • Flexible schema change. Supports SQL, XML, YAML and JSON formats.
  • Auto-generate scripts. Automatically generate SQL scripts for reviews.
  • Real-time monitoring & visibility.
  • Rollbacks
  • Current schema view
  • Schema comparisons
  • Price
Likelihood to Recommend
Some of them are- -Manage version -Manage default data -Help in creating a testing environment.
July 27, 2022

Liquibase is good but needs major enhancement to capture market

Verified User
Team Lead in Information Technology
Banking Company, 10,001+ employees
Score 8 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We are using it for DB Automation solution to promote DB changes on the fly. This product helps in CI-CD workflow for DB changes.
Pros and Cons
  • Script build and deployment
  • Compare script reports
  • Error handling but can be improved
  • DB versions supported
  • the build has a very tedious process - taking backup and restoring for every script to be processed
  • Error handling, many errors are left unmanaged due to which finding the root cause of the issue is difficult
  • HTML reports can be optimized for low space
  • Permissions management i.e. in case of the build is failing, permissions can be checked beforehand. rather than failing in process execution.
  • Project creation from TSV files makes it complicated
Likelihood to Recommend
Liquibase is well suited for CI CD workflow, DB changes, DB differences, and reports.
March 28, 2022

Liquibase

Verified User
Engineer in Information Technology
Banking Company, 1001-5000 employees
Score 7 out of 10
Vetted Review
Verified User
Incentivized
Use Cases and Deployment Scope
We have no tool to manage database schemas. We are looking for an efficient tool that could be used on existing DB2 databases and future postgres databases. The tool needs to be able to start with the existing structure and help us to manage future changes to the databases. An optional use case would be to help developers to mount tests databases with Docker.
Pros and Cons
  • Changelog of existing database
  • easy updates
  • safety with checksums
  • rollbacks
  • Documentation is not always easy to find, for example on tags or rollback definitions in SQL format
  • Weird behaviour if sql file has not the first comment line
Likelihood to Recommend
Liquibase did a good job of creating a changelog of the existing database. But the only well-created format was SQL. Other formats like XML were not quite generated and could not be used on an empty database for updates. Rollbacks with tags are efficient, but it needs to be anticipated as tags are not easy (it's not documented) to add afterward
Return to navigation